X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8F96C.F6EBB508@onstor-exch02.onstor.net>; Fri, 8 Aug 2008 08:39:37 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: palnasg01 - fp1.2
Date: Fri, 8 Aug 2008 08:39:36 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0B3BAB8F@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0B31A8EC@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: palnasg01 - fp1.2
Thread-Index: Acj4BohfKmEqfnUnQJyTDO5YPVq6OAAmDuOgAACBvBQAAOnW0AAFuY6wAAAdUsQAAGjkgAArweww
References: <572F0C094F37344EB2B046EF5508059D05FA56FB@PALMAIL01.lsi.com> <BB375AF679D4A34E9CA8DFA650E2B04E0889C4E9@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0B31A8EC@onstor-exch02.onstor.net>
From: "John Culp" <john.culp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>,
	"Carlos Mora" <carlos.mora@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

Here is an excerpt from an email I sent a customer that was having
similar issues. =20

People will argue that gigabit doesn't negotiate which is partially
true; it doesn't negotiate speed. But, it does negotiate duplex, flow
control parameters, and remote fault information. I believe the issue
has to do with the flow control parameters and how some Ethernet
interfaces can't communicate this information to Cisco's interface's
satisfaction. What can happen is the interface will link up and
function; but, will function poorly due to the flow control or go up and
down. To resolve this problem we would have customers disable this
parameter (enabled by default) and their performance issues would go
away. The Cisco information is listed below and here is the link to the
parameter on Cisco's web page:=20
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/na
tive/configuration/guide/intrface.html#wp1040549

I hope this might help in some way.  If we can help in any other way,
please let us know.
=20
Configuring Link Negotiation on Gigabit Ethernet Ports=20


------------------------------------------------------------------------
--------

Note Link negotiation does not negotiate port speed.=20


------------------------------------------------------------------------
--------

On Gigabit Ethernet ports, link negotiation exchanges flow-control
parameters, remote fault information, and duplex information. Link
negotiation is enabled by default.=20

The ports on both ends of a link must have the same setting. The link
will not come up if the ports at each end of the link are set
inconsistently (link negotiation enabled on one port and disabled on the
other port).=20

Table 9-1 shows the four possible link negotiation configurations and
the resulting link status for each configuration.=20


Table 9-1 Link Negotiation Configuration and Possible Link Status =20
 Link Negotiation State  Link Status =20
Local Port  Remote Port  Local Port  Remote Port =20
Off=20
 Off=20
 Up=20
 Up=20
=20
On=20
 On=20
 Up=20
 Up=20
=20
Off=20
 On=20
 Up=20
 Down=20
=20
On=20
 Off=20
 Down=20
 Up=20
=20




To configure link negotiation on a port, perform this task:=20


   Command  Purpose =20
Step 1 =20
 Router(config)# interface gigabitethernet slot/port=20
 Selects the port to be configured.=20
=20
Step 2 =20
 Router(config-if)# speed nonegotiate=20
 Disables link negotiation.=20
=20
Router(config-if)# no speed nonegotiate=20
 Reverts to the default configuration (link negotiation enabled).=20
=20


This example shows how to enable link negotiation on Gigabit Ethernet
port 5/4:=20

Router(config)# interface gigabitethernet 5/4=20

Router(config-if)# no speed nonegotiate=20

Displaying the Speed and Duplex Mode Configuration=20
To display the speed and duplex mode configuration for a port, perform
this task:=20


 Command  Purpose =20
Router# show interfaces type1 slot/port=20
 Displays the speed and duplex mode configuration.=20
=20
1 type =3D ethernet, fastethernet, gigabitethernet, or =
tengigabitethernet=20
=20




This example shows how to display the speed and duplex mode of Fast
Ethernet port 5/4:=20

Router# show interfaces fastethernet 5/4

FastEthernet5/4 is up, line protocol is up

  Hardware is Cat6K 100Mb Ethernet, address is 0050.f0ac.3058 (bia
0050.f0ac.3058)

  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:33, output never, output hang never

  Last clearing of "show interface" counters never

  Queueing strategy: fifo

  Output queue 0/40, 0 drops; input queue 0/75, 0 drops

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     1238 packets input, 273598 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 input packets with dribble condition detected

     1380 packets output, 514382 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier

     0 output buffer failures, 0 output buffers swapped out

Router#=20
=20


John Culp=20
940-239-7489 Office=20
972-523-4287 Cell=20


-----Original Message-----
From: Brian Stark=20
Sent: Thursday, August 07, 2008 1:47 PM
To: Carlos Mora; dl-cstech
Subject: RE: palnasg01 - fp1.2

This is almost certainly because autonegotiation settings are mismatched
between the switch and filer.  For copper, autonegotation must be off on
both sides.

Once autonegotiation is confirmed to be off and if the problem is still
there, I would then suggest connecting a cable between fp1.2 and fp1.3.
If the link continues to bounce up and down, then it's the filer.  If
the link stays on, then that confirms it's something outside the filer.


Brian
=20

> -----Original Message-----
> From: Carlos Mora
> Sent: Thursday, August 07, 2008 11:31 AM
> To: dl-cstech
> Cc: Carlos Mora
> Subject: FW: palnasg01 - fp1.2
>=20
> LSI has a port that is flapping up and down.
>=20
> They have swapped the sfp, the cable and have checked the port on the=20
> switch.
>=20
> Is there anything else that can be checked before swapping out the=20
> bobcat?
>=20
> Thanks
> Carlos
>=20
> --
> Carlos Mora
> carlos.mora@onstor.com
> ONStor, Inc.
> Sr. Technical Support Engineer
> (408)802-5602
>=20
>=20
>=20
> -----Original Message-----
> From: Chrisley, Deborah J (Deborah) %=20
> [mailto:Deborah.Chrisley@lsi.com]
> Sent: Thu 8/7/2008 2:29 PM
> To: Chrisley, Deborah J (Deborah) %; Carlos Mora; Bill Duffy
> Cc: DLA-IT Storage
> Subject: RE: palnasg01 - fp1.2
> =20
> Anjan, Carlos,
>=20
> No errors on the port side - but Networking can see  the port going up

> and down.
> Dale replaced the cable - but the port is still going up and down.
>=20
> What's the next step?
>=20
> --Deb
>=20
>=20
>=20
> -----Original Message-----
> From: Chrisley, Deborah J (Deborah) %
> Sent: Thursday, August 07, 2008 11:45 AM
> To: Carlos Mora; Bill Duffy
> Cc: DLA-IT Storage
> Subject: RE: palnasg01 - fp1.2
>=20
> I swapped the SFP on the Onstor filers palnasg01 with one on testnas02
>=20
> -----Original Message-----
> From: Carlos Mora [mailto:carlos.mora@onstor.com]
> Sent: Thursday, August 07, 2008 11:18 AM
> To: Chrisley, Deborah J (Deborah) %; Bill Duffy
> Cc: DLA-IT Storage; Carlos Mora
> Subject: RE: palnasg01 - fp1.2
>=20
> Did you swap the port or the SFP on the port? It could be the cable or

> it could be the port on the other end as well, once we rule those out,

> then we assume there is a problem with actual hardware at which point=20
> I will get one of our hw engineers to examine the system and make that

> call.
>=20
> Thanks
> Carlos
>=20
> --
> Carlos Mora
> carlos.mora@onstor.com
> ONStor, Inc.
> Sr. Technical Support Engineer
> (408)802-5602
>=20
>=20
>=20
> -----Original Message-----
> From: Chrisley, Deborah J (Deborah) %=20
> [mailto:Deborah.Chrisley@lsi.com]
> Sent: Thu 8/7/2008 11:04 AM
> To: Chrisley, Deborah J (Deborah) %; Carlos Mora; Bill Duffy
> Cc: DLA-IT Storage
> Subject: RE: palnasg01 - fp1.2
>=20
> I swapped the port on the onstor with an unused one on the test=20
> cluster.
> And the port is still complaining.
>=20
> cable problem?
>=20
> --Deb
>=20
> _____________________________________________
> From:    Chrisley, Deborah J (Deborah) %
> Sent:   Wednesday, August 06, 2008 4:54 PM
> To:     Carlos Mora; Bill Duffy
> Cc:     DLA-IT Storage
> Subject:        palnasg01 - fp1.2
>=20
>=20
> I will unplug the cable going to this port tomorrow morning:
>=20
> Aug  6 16:40:08 palnasg01 : 1:0:ipm:NOTICE: 90688: Port :=20
> fp1.2 is UP Aug  6 16:40:08 palnasg01 : 1:0:ipm:NOTICE:=20
> 90689: luc_link_up:298: lport fp1.2 UP Aug  6 16:40:08
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:41:00 palnasg01 : 1:0:ipm:NOTICE: 90690: Port :=20
> fp1.2 is DOWN Aug  6 16:41:00 palnasg01 : 1:0:ipm:NOTICE:=20
> 90691: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:41:00 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:41:02 palnasg01 : 1:0:ipm:NOTICE: 90692: Port :=20
> fp1.2 is UP Aug  6 16:41:02 palnasg01 : 1:0:ipm:NOTICE:=20
> 90693: luc_link_up:298: lport fp1.2 UP Aug  6 16:41:02
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:41:38 palnasg01 : 1:0:ipm:NOTICE: 90694: Port :=20
> fp1.2 is DOWN Aug  6 16:41:38 palnasg01 : 1:0:ipm:NOTICE:=20
> 90695: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:41:38 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:41:40 palnasg01 : 1:0:ipm:NOTICE: 90696: Port :=20
> fp1.2 is UP Aug  6 16:41:40 palnasg01 : 1:0:ipm:NOTICE:=20
> 90697: luc_link_up:298: lport fp1.2 UP Aug  6 16:41:40
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:43:06 palnasg01 : 1:0:ipm:NOTICE: 90698: Port :=20
> fp1.2 is DOWN Aug  6 16:43:06 palnasg01 : 1:0:ipm:NOTICE:=20
> 90699: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:43:06 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:43:08 palnasg01 : 1:0:ipm:NOTICE: 90700: Port :=20
> fp1.2 is UP Aug  6 16:43:08 palnasg01 : 1:0:ipm:NOTICE:=20
> 90701: luc_link_up:298: lport fp1.2 UP Aug  6 16:43:08
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:43:18 palnasg01 : 1:0:ipm:NOTICE: 90702: Port :=20
> fp1.2 is DOWN Aug  6 16:43:18 palnasg01 : 1:0:ipm:NOTICE:=20
> 90703: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:43:18 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:43:22 palnasg01 : 1:0:ipm:NOTICE: 90704: Port :=20
> fp1.2 is UP Aug  6 16:43:22 palnasg01 : 1:0:ipm:NOTICE:=20
> 90705: luc_link_up:298: lport fp1.2 UP Aug  6 16:43:22
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:43:24 palnasg01 : 1:0:ipm:NOTICE: 90706: Port :=20
> fp1.2 is DOWN Aug  6 16:43:24 palnasg01 : 1:0:ipm:NOTICE:=20
> 90707: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:43:24 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:43:26 palnasg01 : 1:0:ipm:NOTICE: 90708: Port :=20
> fp1.2 is UP Aug  6 16:43:26 palnasg01 : 1:0:ipm:NOTICE:=20
> 90709: luc_link_up:298: lport fp1.2 UP Aug  6 16:43:26
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:45:18 palnasg01 : 1:0:ipm:NOTICE: 90710: Port :=20
> fp1.2 is DOWN Aug  6 16:45:18 palnasg01 : 1:0:ipm:NOTICE:=20
> 90711: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:45:18 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:45:22 palnasg01 : 1:0:ipm:NOTICE: 90712: Port :=20
> fp1.2 is UP Aug  6 16:45:22 palnasg01 : 1:0:ipm:NOTICE:=20
> 90713: luc_link_up:298: lport fp1.2 UP Aug  6 16:45:22
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:45:28 palnasg01 : 1:0:ipm:NOTICE: 90714: Port :=20
> fp1.2 is DOWN Aug  6 16:45:28 palnasg01 : 1:0:ipm:NOTICE:=20
> 90715: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:45:28 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:45:32 palnasg01 : 1:0:ipm:NOTICE: 90716: Port :=20
> fp1.2 is UP Aug  6 16:45:32 palnasg01 : 1:0:ipm:NOTICE:=20
> 90717: luc_link_up:298: lport fp1.2 UP Aug  6 16:45:32
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:49:26 palnasg01 : 1:0:ipm:NOTICE: 90718: Port :=20
> fp1.2 is DOWN Aug  6 16:49:26 palnasg01 : 1:0:ipm:NOTICE:=20
> 90719: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:49:26 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:49:28 palnasg01 : 1:0:ipm:NOTICE: 90720: Port :=20
> fp1.2 is UP Aug  6 16:49:28 palnasg01 : 1:0:ipm:NOTICE:=20
> 90721: luc_link_up:298: lport fp1.2 UP Aug  6 16:49:28
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:50:14 palnasg01 : 1:0:ipm:NOTICE: 90722: Port :=20
> fp1.2 is DOWN Aug  6 16:50:14 palnasg01 : 1:0:ipm:NOTICE:=20
> 90723: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:50:14 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:50:16 palnasg01 : 1:0:ipm:NOTICE: 90724: Port :=20
> fp1.2 is UP Aug  6 16:50:16 palnasg01 : 1:0:ipm:NOTICE:=20
> 90725: luc_link_up:298: lport fp1.2 UP Aug  6 16:50:16
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
> Aug  6 16:50:34 palnasg01 : 1:0:ipm:NOTICE: 90726: Port :=20
> fp1.2 is DOWN Aug  6 16:50:34 palnasg01 : 1:0:ipm:NOTICE:=20
> 90727: luc_link_down: 356: lport fp1.2 DOWN.
> Aug  6 16:50:34 palnasg01 : 0:0:eventd:NOTICE: Process-EVENT
> Port: fp1.2 State Down, Msg ''
> Aug  6 16:50:36 palnasg01 : 1:0:ipm:NOTICE: 90728: Port :=20
> fp1.2 is UP Aug  6 16:50:36 palnasg01 : 1:0:ipm:NOTICE:=20
> 90729: luc_link_up:298: lport fp1.2 UP Aug  6 16:50:36
> palnasg01 : 0:0:eventd:NOTICE: Process-EVENT Port: fp1.2 State Up, Msg

> ''
>=20
>=20
>=20
>=20
